Edit Task: NonRecurringSTKReports
Format
SCHED / EditTask '<TaskName>' NonRecurringSTKReports <# STKReports> <Rep1Start> <Rep1Stop> <Rep1WindowType> <Rep1StartOffset> <Rep1StopOffset> <Rep1Duration> '<Rep1STKObj1>' '<Rep1STKObj2>' '<Rep1ReportName>' <Rep1MaintTimeOffset> ... <RepNStart> <RepNStop> <RepNWindowType> <RepNStartOffset> <RepNStopOffset> <RepNDuration> '<RepNSTKObj1>' '<RepNSTKObj2>' '<RepNReportName>' <RepNMaintTimeOffset>
Description
The NonRecurringSTKReports attribute under EditTask defines a number of STK Report Definitions and any previous STK Report Definitions are deleted.
Parameters
| Parameter | Description |
|---|---|
| # STK Reports | An integer value indicating the number of STK Report definitions that are contained within the command. |
| Start/Stop | The format is YYYY/MM/DD_HH:MM:SS or YYYY/MM/DD_HH:MM:SS.fff. |
| RepNWindowType | Options are either 'FixedStart' or 'FixedStop'. This parameter is only required for Single Time type reports (ascending node, AOS, etc.). If not used, a filler such as 'None' should be used instead. Other report types can be automatically determined based on the selected report style name (Access, Range, etc.). |
| RepNStartOffset | A number representing seconds (millisecond fidelity) for Single Time type reports or Value1 for a Value type report. This value should be ignored for Single Time type reports where the WindowType is set to FixedStop. |
| RepNStopOffset | A number representing seconds (millisecond fidelity) for Single Time type reports or Value2 for a Value type report. This value should be ignored for Single Time type reports where the WindowType is set to FixedStart. |
| RepNDuration | The parameter should be entered as a number representing seconds (millisecond fidelity). If the number is negative, the report will be set to work as if the Next Time Value In Report Option in the STK Time Report Form is checked (True), which means each window will be as long as the time between each report value.
The parameter is ignored if <RepNWindowType> is set to 'Window' or 'ValueRange'. |
| RepNSTKObj1 | A string of text in single quotes of the STKObject path, not including the scenario name (ex. 'Satellite/FUSE'). Empty string is not allowed and the parameter is case sensitive. |
| RepNSTKObj2 | A string of text in single quotes of the STKObject path, not including the scenario name (ex. 'Satellite/TRACE'). The parameter is case sensitive and an empty string is allowed for reports that only use 1 STK Object. |
| RepNReportName | A string of text in single quotes of the STK Report type. This value must be compatible with the number of defined STK Objects defined for STKObj1 and STKObj2. Empty string is not allowed and the report name is case sensitive. |
| RepNMaintTimeOffset | Options are either yes or no and an empty string is not allowed. If yes, then any report Start/Stop time offsets from schedule Start/Stop times are maintained if schedule Start/Stop times are changed. |
Examples
Use an STK sun report to limit when a task can be completed.
SCHED / EditTask 'FUSEscience' NonRecurringSTKReports 1 2014/01/01_00:00:00.000 2014/01/03_00:00:00.000 Window 0 0 0 'Satellite/FUSE' '' 'Sun' YES
Use an STK report so that the task can only be completed when the spacecraft is between 5 degrees and 15 degrees latitude. The -1 is not used.
SCHED / EditTask 'Contact' NonRecurringSTKReports 1 2014/01/01_00:00:00 2014/01/03_00:00:00 None 5 25 -1 'Satellite/TRACE' '' 'Latitude' No
Use an STK report so that the task can only be completed during an 11 minute window after each time the spacecraft hits apogee. The -1 is not used.
SCHED / EditTask 'Maneuver' NonRecurringSTKReports 1 2014/01/01_00:00:00 2014/01/03_00:00:00 FixedStart 0 -1 660 'Satellite/FUSE' '' 'Apogee' No
Use an STK report so that the task can only be completed during a 1 hour window before umbra start for the spacecraft. The -1 is not used.
SCHED / EditTask 'Maneuver' NonRecurringSTKReports 1 2014/01/01_00:00:00 2014/01/03_00:00:00 FixedStop -1 0 660 'Satellite/ISS' '' 'Umbra Start' No
